language en

Linked.Archi LeanIX Meta Model v3 Ontology

Release: 2019-03-17

Modified on: 2026-04-12
This version:
https://meta.linked.archi/leanix/v3/onto/3.0.0#
Revision:
3
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
See also:
https://help.sap.com/docs/leanix/ea/meta-model
https://help.sap.com/docs/leanix/ea/modeling-guidelines-v3
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Kalin Maldzhanski. Linked.Archi LeanIX Meta Model v3 Ontology. Revision: 3. Retrieved from: https://meta.linked.archi/leanix/v3/onto/3.0.0#
Provenance of this page
deprecated

Linked.Archi LeanIX Meta Model v3 Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Annotation Properties

Linked.Archi LeanIX Meta Model v3 Ontology: Description back to ToC

Ontology representation of SAP LeanIX Meta Model v3 fact sheets and relations. This is not an official SAP document.

Cross-reference for Linked.Archi LeanIX Meta Model v3 Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi LeanIX Meta Model v3 Ontology.

Classes

Applicationc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#Application

Application fact sheet representing business or technical application systems in Meta Model v3, without the explicit v4 subtypes.
Example
"CRM Core", "Data Warehouse" or "Intranet Portal" modeled as Application fact sheets in v3.
has super-classes
Fact Sheet c

Business Capabilityc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#BusinessCapability

Business capability concept in v3 describing what the organization does or can do; typically reused when migrating to v4.
Example
Capabilities such as "Order Management", "Customer Billing" or "Supplier Management".
has super-classes
Fact Sheet c

Data Objectc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#DataObject

Logical data entity fact sheet in v3 that is shared across applications and processes.
Example
Data objects such as "Customer", "Invoice", "Product" or "Payment".
has super-classes
Fact Sheet c

Fact Sheetc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#FactSheet

Abstract supertype for all LeanIX fact sheet instances in Meta Model v3.
Example
Any Application, Project, User Group or IT Component fact sheet is also an instance of :FactSheet.
has super-classes
element c
has sub-classes
Application c, Business Capability c, Data Object c, IT Component c, Interface c, Process c, Product c, Project c, Provider c, Tech Category c, Tech Platform c, User Group c

Interfacec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#Interface

Integration link or interface fact sheet in v3 that connects source and target applications and exchanges data.
Example
A nightly "File transfer from CRM to ERP" interface or a near‑real‑time "Customer API" interface.
has super-classes
Fact Sheet c

IT Componentc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#ITComponent

Technical component such as a software product, runtime, database or infrastructure element used by applications in v3.
Example
"Oracle Database 19c", "Windows Server 2022" or "Apache Kafka Cluster" as IT Components.
has super-classes
Fact Sheet c

Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#Process

Top‑level process fact sheet in v3 describing business processes before the introduction of the Business Context concept in v4.
Example
Processes such as "Order to Cash", "Hire to Retire" or "Record to Report".
has super-classes
Fact Sheet c

Productc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#Product

Product or service offering fact sheet in v3; later treated as a subtype of Business Context in v4.
Example
"Gold Credit Card", "Standard Current Account" or "Premium Support Package" products.
has super-classes
Fact Sheet c

Projectc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#Project

Project‑like change initiative in v3 that delivers scope such as new applications, process changes or technology rollouts.
Example
"CRM Replacement 2025" or "Data Center Exit" projects.
has super-classes
Fact Sheet c

Providerc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#Provider

Vendor or provider that supplies IT Components or SaaS Applications in v3.
Example
Providers such as "SAP", "Microsoft Azure", "AWS" or an internal IT shared‑services organization.
has super-classes
Fact Sheet c

Tech Categoryc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#TechCategory

Category used to group IT Components into coherent sets for classification and reporting in v3.
Example
Categories like "Database", "Middleware", "Operating System" or "Network Equipment".
has super-classes
Fact Sheet c

Tech Platformc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#TechPlatform

Optional v3 fact sheet type representing a technical platform composed of multiple IT Components.
Example
"Integration Platform" grouping ESB, API gateway and messaging infrastructure as a TechPlatform.
has super-classes
Fact Sheet c

User Groupc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/v3/onto#UserGroup

Grouping of users or stakeholders that consume applications or participate in processes, modeled as User Groups in v3.
Example
"Finance Users Germany" or "Global Sales Users" modeled as UserGroup fact sheets.
has super-classes
Fact Sheet c

Annotation Properties

change noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#changeNote

createdap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/created

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/creator

definitionap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#definition

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/description

exampleap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#example

history noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#historyNote

is replaced byap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/isReplacedBy

licenseap back to ToC or Annotation Property ToC

IRI: http://creativecommons.org/ns#license

modifiedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/modified

pref labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#prefLabel

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/publisher

scope noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#scopeNote

statusap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/status

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/title

Legend back to ToC

c: Classes

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.